QRZ! Ham Radio 4/QRZ Ham Radio Callsign Database - Volume 4.iso/digests/tcp/940208.txt

Internet Message Format | 1994-11-13 | 36KB

Date: Wed, 21 Sep 94 04:30:02 PDT
From: Advanced Amateur Radio Networking Group <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: TCP-Group Digest V94 #208
To: tcp-group-digest


TCP-Group Digest            Wed, 21 Sep 94       Volume 94 : Issue  208

Today's Topics:
                           GCC port of NOS
                                 help
                        Mail failure (3 msgs)
                     mtu oddity, jnos, and linux
                         SCC Testing (2 msgs)
                    upload W-NOS.940921.zip [src]

Send Replies or notes for publication to: <[e-mail]>.
Subscription requests to <[e-mail]>.
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: Tue, 20 Sep 1994 22:00:46 -0700
From: Phil Karn <[e-mail]>
Subject: GCC port of NOS
To: [e-mail]

I've decided to do the port of NOS to DJGCC (the DOS port of GCC).
Turns out there is full support for calling real-mode routines;
there's even a demonstration program in the package that shows how to
call a FTP Software Packet Driver (which was my concern for some time).

I'm doing this in stages. Stage 1 is to rename external symbols that
conflict with those in the GCC libraries. E.g., psignal() will become
ksignal(), alarm() will become kalarm(), etc. At the same time I will
attempt to clean up the code to make it compile more cleanly.

During this phase I will try to retain backward compatibility with
Borland C++ 3.1. When I'm done I'll package everything up and release
it as my last Borland-based version. Then I'll start stage 2:
translating assembler code and writing any new C code specifically
required to run under DJGPP.

There are several good reasons for this effort. One is the vastly
increased memory space available in protected mode; you'll actually be
able to use all that RAM for something useful. I may add some
memory-intensive facilities that haven't been practical under DOS,
e.g., extended debugging for mbufs and memory blocks. (One drawback to
running in protected mode -- the incentive to find and fix minor memory
leaks is considerably reduced!)

Another reason to switch to protected mode is better
performance. 32-bit operations in real mode require override prefixes
that take extra cycles to execute. And I may be able to switch to
faster but more memory-intensive algorithms in places where they make
a difference (e.g., IP routing and the malloc() storage allocator).

One drawback: DJGPP executables require a 386 or better. Personally, I
just don't see this as much of a problem nowadays. Those with 286s can
always continue to run Borland-based versions.

Phil

------------------------------

Date: Tue, 20 Sep 94 22:18:38
From: [e-mail]
Subject: help
To: [e-mail]

>From Steve Sampson
"All you have to do is become mature giving adults, instead of snickering
children"

This was in response to, what I thought was, a rather humorous commentary on
the rash of help msgs this group has been receiving. Since, according to
Steve's logic, I could only be one child, I thought I'd share this with my
siblings. As I have mentioned privately to others on the list, I intended
that in the nature of...well close your eyes and visualize Andy Rooney
saying it.

For those that have critized me for my comments (and you know who you are),
how many of you have answered these people back asking them what exactly
they needed help with? I still maintain it takes only a few more keystrokes
to say, HELP I am trying to [un]subscribe.
In fairness, to Steve, he did have a good suggestion, that is to place
occationally (or always) instructions in the digest on how to get in or out
of the list.


-Walt

------------------------------

Date: Tue, 20 Sep 94 15:09:00 edt
From: Adminstrator <[e-mail]>
Subject: Mail failure
To: dayhub!3445a!ucsd.edu![e-mail]


User mail received addressed to the following unknown addresses:
  GPPGDAYTON/GPPGPOST/lshannon

------------------------------------------------------------------------------
Return-Path: <dayhub!3445a!ucsd.edu![e-mail]>
Received: from prowler.daytonoh.ncr.com by gppgpost.daytonoh.ncr.com id
    <[e-mail]>; Tue, 20 Sep 94 15:09:41 edt
Received: by prowler.daytonoh.ncr.com; 20 Sep 94 15:05:36 EDT
Received: by dayhub.DaytonOH.NCR.COM; 20 Sep 94 15:05:26 EDT
Received: by 3445a.DaytonOH.NCR.COM; 20 Sep 94 15:05:28 EDT id AA780086896
    Tue, 20 Sep 94 14:48:16 EST
Date: Tue, 20 Sep 94 14:48:16 EST
From: [e-mail]
Message-Id: <[e-mail]>
To: [e-mail]
Subject: TCP-Group Digest V94 #204


>From ncrhub1!ucsd.edu![e-mail]
X-Envelope-From: ncrhub1!ucsd.edu![e-mail]
Received: by 3445a.DaytonOH.NCR.COM; 16 Sep 94 13:29:52 EDT
Received: by dayhub.DaytonOH.NCR.COM; 16 Sep 94 13:28:42 EDT
Received: from ncrgw2 by ncrhub1.NCR.COM id dp05180; 16 Sep 94 13:18 EDT
Received: by ncrgw2.NCR.COM; 16 Sep 94 11:19:36 EDT
    sendmail 8.6.9/UCSD-2.2-sun
    Fri, 16 Sep 1994 04:30:12 -0700 for tcp-digest-list
Received: by ucsd.edu; id EAA09993
    sendmail 8.6.9/UCSD-2.2-sun
    Fri, 16 Sep 1994 04:30:09 -0700 for tcp-group-ddist
Message-Id: <[e-mail]>
Date: Fri, 16 Sep 94 04:30:02 PDT
From: Advanced Amateur Radio Networking Group <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: TCP-Group Digest V94 #204
To: [e-mail]

TCP-Group Digest            Fri, 16 Sep 94       Volume 94 : Issue  204

Today's Topics:
        A Packet Driver to go on air with a KISS TNC (2 msgs)
                     Cross compile NOS with gcc?
                        Mail failure (2 msgs)
                    uploaded ftp.ucsd.edu wnos.exe

Send Replies or notes for publication to: <[e-mail]>.
Subscription requests to <[e-mail]>.
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: Thu, 15 Sep 94 21:48:01 +02
From: "Alessandro Agostini" <[e-mail]>
Subject: A Packet Driver to go on air with a KISS TNC
To: [e-mail]

For Ham-radio community there is NOS which permits to make experience of tcpip
through amateur radio channals with a TNC.
The second step: We have a tcp-appl. of our interest, for example a Gopher
Client , a Telbin or something else ... and we would like to use it with a
KISSmode TNC to log to our area-router on air.
The problem: Our appl. doesn't threat beyond IP level: We need something
to encapsulate the datagrams in an AX25 point to point UI link. We need
a KISS-TNC packet driver.
If we look at the SLIP8250 Packet Driver we see it to be a serial
link point to point driver not very far from what we need. Thus by adding
a simple AX25 header to every outgoing frame and the minimum overhead to pass
through a kiss-tnc we can easily operate an application like PCG3 (which is a
gopher client) on air.
This is what I did. I have changed little in slip8250 (naming it kiss8250!)
and corrently using it as an interface between any tcpip appl passing
through the air.
If any Ham is interested in developing a 'real' packet driver starting
from this simple experience feel free to call. 73 TNX DE IK5HGN

------------------------------

Date: Thu, 15 Sep 94 22:50 EDT
From: [e-mail] (Russell Nelson)
Subject: A Packet Driver to go on air with a KISS TNC
To: [e-mail]

   Date: Thu, 15 Sep 94 21:48:01 +02
   From: "Alessandro Agostini" <[e-mail]>

   If we look at the SLIP8250 Packet Driver we see it to be a serial
   link point to point driver not very far from what we need.

And surely you noticed that I had intended that from the start!  The
code decides at runtime whether it self-identifies as SLIP, KISS, or
AX25.  No one every wrote the code for KISS or AX25, but the potential
is there...

-russ <[e-mail]>    http://www.crynwr.com/crynwr/nelson.html
Crynwr Software   | Crynwr Software sells packet driver support | ask4 PGP key
11 Grant St.      | [phone] (9201 FAX)  | What is thee doing about it?
Potsdam, NY 13676 | LPF member - ask me about the harm software patents do.

------------------------------

Date: Thu, 15 Sep 1994 10:37:50 -0500 (CDT)
From: Don Loflin <[e-mail]>
Subject: Cross compile NOS with gcc?
To: Phil Karn <[e-mail]>

On Wed, 14 Sep 1994, Phil Karn wrote:

> I've never built NOS with gcc, but I'm *this close* to abandoning
> Borland C altogether and going to DJGCC.
>
> The only thing holding me back is the learning curve for
> DJGCC. Anybody out there with experience, or who can point me to a FAQ
> so I can come up to speed?

Never used DJGCC, but if it really has a high learning curve, check out
EMX/GCC.  It's a darn fine port of GCC which does support DOS, though you
may have only heard of it associated with OS/2.  It can be run under DOS,
and I think the process is even easier if you get RSX (from CICA/mirrors
programmr/dpmigcc4.zip) and put rsx.exe in the bin directory with gcc.exe
et al.  Then just run gcc/make/whatever.  Plug in RCS and you're set.

Others will have to comment on the code & library differences between
DJGCC & EMX/GCC.

--Don Loflin

------------------------------

Date: Thu, 15 Sep 94 10:18:00 edt
From: Adminstrator <[e-mail]>
Subject: Mail failure
To: dayhub!3445a!ucsd.edu![e-mail]



User mail received addressed to the following unknown addresses:
  GPPGDAYTON/GPPGPOST/lshannon


------------------------------------------------------------------------------

Return-Path: <dayhub!3445a!ucsd.edu![e-mail]>
Received: from prowler.daytonoh.ncr.com by gppgpost.daytonoh.ncr.com id
    <[e-mail]>; Thu, 15 Sep 94 10:18:47 edt
Received: by prowler.daytonoh.ncr.com; 14 Sep 94 15:24:57 EDT
Received: by dayhub.DaytonOH.NCR.COM; 14 Sep 94 15:24:51 EDT
Received: by 3445a.DaytonOH.NCR.COM; 14 Sep 94 15:24:53 EDT id AA779571782
    Wed, 14 Sep 94 15:43:02 EST
Date: Wed, 14 Sep 94 15:43:02 EST
From: [e-mail]
Message-Id: <[e-mail]>
To: [e-mail]
Subject: TCP-Group Digest V94 #202

Large message has been converted into an attachment.

------------------------------

Date: Thu, 15 Sep 94 12:38:00 edt
From: Adminstrator <[e-mail]>
Subject: Mail failure
To: dayhub!3445a!ucsd.edu![e-mail]



User mail received addressed to the following unknown addresses:
  GPPGDAYTON/GPPGPOST/lshannon


------------------------------------------------------------------------------

Return-Path: <dayhub!3445a!ucsd.edu![e-mail]>
Received: from prowler.daytonoh.ncr.com by gppgpost.daytonoh.ncr.com id
    <[e-mail]>; Thu, 15 Sep 94 12:38:52 edt
Received: by prowler.daytonoh.ncr.com; 15 Sep 94 12:34:58 EDT
Received: by dayhub.DaytonOH.NCR.COM; 15 Sep 94 12:34:50 EDT
Received: by 3445a.DaytonOH.NCR.COM; 15 Sep 94 12:35:03 EDT id AA779647902
    Thu, 15 Sep 94 12:51:42 EST
Date: Thu, 15 Sep 94 12:51:42 EST
From: [e-mail]
Message-Id: <[e-mail]>
To: [e-mail]
Subject: TCP-Group Digest V94 #203


Received: by ccmail from 3445a.DaytonOH.NCR.COM
>From ncrhub1!ucsd.edu![e-mail]
X-Envelope-From: ncrhub1!ucsd.edu![e-mail]
Received: by 3445a.DaytonOH.NCR.COM; 15 Sep 94 12:30:04 EDT
Received: by dayhub.DaytonOH.NCR.COM; 15 Sep 94 12:29:32 EDT
Received: from ncrgw1 by ncrhub1.NCR.COM id bm10928; 15 Sep 94 12:08 EDT
Received: by ncrgw1.NCR.COM; 15 Sep 94 12:03:07 EDT
    sendmail 8.6.9/UCSD-2.2-sun
    Thu, 15 Sep 1994 04:30:08 -0700 for tcp-digest-list
Received: by ucsd.edu; id EAA15098
    sendmail 8.6.9/UCSD-2.2-sun
    Thu, 15 Sep 1994 04:30:06 -0700 for tcp-group-ddist
Message-Id: <[e-mail]>
Date: Thu, 15 Sep 94 04:30:02 PDT
From: Advanced Amateur Radio Networking Group <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: TCP-Group Digest V94 #203
To: [e-mail]

TCP-Group Digest            Thu, 15 Sep 94       Volume 94 : Issue  203

Today's Topics:
                 ax25 linux implementation? (2 msgs)
                     Cross compile NOS with gcc?
                                 help
                     wampes and net takes all cpu

Send Replies or notes for publication to: <[e-mail]>.
Subscription requests to <[e-mail]>.
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: Wed, 14 Sep 94 07:53:07 -0500
From: [e-mail] (WALT DUBOSE - K5YFW)
Subject: ax25 linux implementation?
To: [e-mail]

Hey, digi's are Ok, as along as they work at 19.2Kbps or better and
are 1200 ft AGL.  But data repeaters (that will handle 19.2Kbps or
better and are 1200 ft AGL) are better as you just play with the RX/TX
frequencies and not the software.           -- K5YFW

In Gerry's message of 14 Sep 1994 at 0536 CDT, he writes:
> Rob sez:
> >
> > *** In reply to mail from Brian Kantor, ....:
> > > The way you handle direct vs digi paths to stations is
> > >
> > > 1) get rid of the digi.  Dynamite is good  Digipeaters suck hard and
> > > really need to be gotten rid of as fast as possible.  If this helps, so
> > > much the better.
> >
> > This'll give the digi 'a larger coverage area', is this what we want ?
> >
> > Dozing it in might be safer ... ;-)
>
> With dynamite, you disperse it overa larger area both reducing the overall
> impact of the original problem, and making it harder for the EPA to figure
out
> what it was to cite you.  If you doze and bury it, it's a point source of
> contamination... ;-)
>
> Gerry
>

------------------------------

Date: Wed, 14 Sep 1994 21:00:46 -0700
From: Phil Karn <[e-mail]>
Subject: ax25 linux implementation?
To: [e-mail]

I fully agree with Brian's suggestions. They're mostly consistent with
the way NOS already does it. I used to do it differently, but changed
to the present scheme because it was so much cleaner. You really don't
want variable length ARP packets and monster sockaddr structures.

Phil

------------------------------

Date: Wed, 14 Sep 1994 21:11:13 -0700
From: Phil Karn <[e-mail]>
Subject: Cross compile NOS with gcc?
To: [e-mail]

I've never built NOS with gcc, but I'm *this close* to abandoning
Borland C altogether and going to DJGCC.

The only thing holding me back is the learning curve for
DJGCC. Anybody out there with experience, or who can point me to a FAQ
so I can come up to speed?

Phil

------------------------------

Date: Wed, 14 Sep 94 16:12 GMT+0200
From: [e-mail] (Domenico Dato)
Subject: help
To: [e-mail]

help

------------------------------

Date: Thu, 15 Sep 94 11:11:50 EST
From: BARRY TITMARSH <[e-mail]>
Subject: wampes and net takes all cpu
To: Olaf Erb dc1ik <[e-mail]>,

Ok fixed.. during the reinstall on linux, i over looked the fact
that wampes was still expecting a local route via slip and a ttyp0
and on the linux side i forgot to setup the slattach for the ptyp0
and ifconfig sl0 it...
think that this is a known bug in wampes if a route/iface via pty's
is left hanging high and dry.
all functioning correctly now..
Thanks. Barry..

------------------------------

End of TCP-Group Digest V94 #203
******************************

------------------------------

Date: Thu, 15 Sep 94 14:12:15 EST
From: BARRY TITMARSH <[e-mail]>
Subject: uploaded ftp.ucsd.edu wnos.exe
To: TCP-GROUP <[e-mail]>, wnos-group <[e-mail]>

Ok due to many wnos users complaining to me via email and S.F about
my policy of source code only distribution, as of 12:15Z I uploaded
to ftp.ucsd.edu:hamradio/packet/tcpip/incoming/wnos-940815.exe
this is built with:
scc asy netrom all cli/srv nntp pop etc. packet drv etc.
Its without any warrenty, use at your risk.
its complied in 286 mode, i have had this same version running as
a cut down router between ethernet and 4 ax25 ccts running now 36 days
and its lost 15kb memory. from startup.
i have on avg 12-15 ac25 connects via it or useing it. It for MY config
is very stable,

Enjoy..  Barry gm8sau/dc0hk

------------------------------

End of TCP-Group Digest V94 #204
******************************

------------------------------

Date: Tue, 20 Sep 94 15:28:00 edt
From: Adminstrator <[e-mail]>
Subject: Mail failure
To: dayhub!3445a!ucsd.edu![e-mail]


User mail received addressed to the following unknown addresses:
  GPPGDAYTON/GPPGPOST/lshannon

------------------------------------------------------------------------------
Return-Path: <dayhub!3445a!ucsd.edu![e-mail]>
Received: from prowler.daytonoh.ncr.com by gppgpost.daytonoh.ncr.com id
    <[e-mail]>; Tue, 20 Sep 94 15:28:57 edt
Received: by prowler.daytonoh.ncr.com; 20 Sep 94 15:22:39 EDT
Received: by dayhub.DaytonOH.NCR.COM; 20 Sep 94 15:22:29 EDT
Received: by 3445a.DaytonOH.NCR.COM; 20 Sep 94 15:22:30 EDT id AA780089023
    Tue, 20 Sep 94 15:23:43 EST
Date: Tue, 20 Sep 94 15:23:43 EST
From: [e-mail]
Message-Id: <[e-mail]>
To: [e-mail]
Subject: TCP-Group Digest V94 #207


>From ncrhub1!ucsd.edu![e-mail]
X-Envelope-From: ncrhub1!ucsd.edu![e-mail]
Received: by 3445a.DaytonOH.NCR.COM; 20 Sep 94 11:22:11 EDT
Received: by dayhub.DaytonOH.NCR.COM; 20 Sep 94 11:21:37 EDT
Received: from ncrgw1 by ncrhub1.NCR.COM id bk00099; 20 Sep 94 11:18 EDT
Received: by ncrgw1.NCR.COM; 20 Sep 94 11:04:27 EDT
    sendmail 8.6.9/UCSD-2.2-sun
    Tue, 20 Sep 1994 04:30:07 -0700 for tcp-digest-list
Received: by ucsd.edu; id EAA17064
    sendmail 8.6.9/UCSD-2.2-sun
    Tue, 20 Sep 1994 04:30:05 -0700 for tcp-group-ddist
Message-Id: <[e-mail]>
Date: Tue, 20 Sep 94 04:30:02 PDT
From: Advanced Amateur Radio Networking Group <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: TCP-Group Digest V94 #207
To: [e-mail]

TCP-Group Digest            Tue, 20 Sep 94       Volume 94 : Issue  207

Today's Topics:
                      Best asy speed settings?
                          help msgs (2 msgs)
                              SUBSCRIBE

Send Replies or notes for publication to: <[e-mail]>.
Subscription requests to <[e-mail]>.
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: Mon, 19 Sep 1994 09:50:00 -0700
From: Ken Koster <[e-mail]>
Subject: Best asy speed settings?
To: [e-mail]

>Given JNOS 1.10f running on a 386/20 with 16550s on all serial ports, what's
>the best strategy for serial port speeds to the KISS TNCs?  We're looking at
>a switch that will have two 9600 baud TNCs, and probably two 1200 baud ones,
>as well as a couple of PI cards and an ethernet board.  It'll be a busy
>machine...

John, here in the Seattle area we're running one of our primary local switches
(seanvg.ampr.org - 386sx-16) with eight ports.  Two at 19.2, five at 9600 and
one at 4800.  Using 16550's there are no problems with overruns or garbaged
calls
.
We run the system as only a router and conference server so unless you have a
heavy mail load I would suspect your machine to have no problems.

>To reduce latency, we would want to run the ports as fast as possible, at
least
>2x the radio speed.  But from an interrupt and system loading perspective,
are

I'm a firm believer in keeping latency to the minimum, two of our five 9600
ports

will be going to 19.2 soon and I'd push them faster if I could.


73's, Ken  N7IPB

------------------------------

Date: Mon, 19 Sep 94 11:49:34
From: [e-mail]
Subject: help msgs
To: [e-mail]

Has anyone ever figured out whats going on with those people that insist on
sending no titled, single line single sylable msgs to us consisting of the,
all capitalized, word

HELP

Are they being raped?
Are they being bludgeoned?
Are they drowning?
Do they have a flat tire and need a lift? (jnos goes mobile?)
Is it last call at their local bar and they are still alone?
Is that a secret msg for Captain Internet to come to their rescue?, I though
I recently saw a black Stingray flying down Dulles Access Road.

I don't know about the rest of you, but I am curous about this.

-Walt

------------------------------

Date: Mon, 19 Sep 94 19:04:00 -0000
From: [e-mail] (Mike Bilow)
Subject: help msgs
To: [e-mail]

 k> Has anyone ever figured out whats going on with those
 k> people that insist on
 k> sending no titled, single line single sylable msgs to us
 k> consisting of the,
 k> all capitalized, word

 k> HELP

They think we are a collective automatic mail server, like the Usenet Oracle.

:-)

-- Mike

------------------------------

Date: Mon, 19 Sep 94 22:40:12 EDT
From: [e-mail]
Subject: SUBSCRIBE
To: [e-mail]

SUBSCRIBE [e-mail] Herman W Strelow

------------------------------

Date: Mon, 19 Sep 94 11:46:08 UTC
From: [e-mail] (Oddleiv Tungland)
To: [e-mail]

unsubscribe

------------------------------

Date: Mon, 19 Sep 94 11:46:01 UTC
From: [e-mail] (Oddleiv Tungland)
To: [e-mail]

help

------------------------------

End of TCP-Group Digest V94 #207
******************************

------------------------------

Date: Tue, 20 Sep 94 15:41:00 edt
From: Adminstrator <[e-mail]>
Subject: Mail failure
To: dayhub!3445a!ucsd.edu![e-mail]


User mail received addressed to the following unknown addresses:
  GPPGDAYTON/GPPGPOST/lshannon

------------------------------------------------------------------------------
Return-Path: <dayhub!3445a!ucsd.edu![e-mail]>
Received: from prowler.daytonoh.ncr.com by gppgpost.daytonoh.ncr.com id
    <[e-mail]>; Tue, 20 Sep 94 15:41:53 edt
Received: by prowler.daytonoh.ncr.com; 20 Sep 94 15:35:25 EDT
Received: by dayhub.DaytonOH.NCR.COM; 20 Sep 94 15:35:16 EDT
Received: by 3445a.DaytonOH.NCR.COM; 20 Sep 94 15:35:27 EDT id AA780089056
    Tue, 20 Sep 94 15:24:16 EST
Date: Tue, 20 Sep 94 15:24:16 EST
From: [e-mail]
Message-Id: <[e-mail]>
To: [e-mail]
Subject: TCP-Group Digest V94 #206


>From ncrhub1!ucsd.edu![e-mail]
X-Envelope-From: ncrhub1!ucsd.edu![e-mail]
Received: by 3445a.DaytonOH.NCR.COM; 19 Sep 94 13:52:34 EDT
Received: by dayhub.DaytonOH.NCR.COM; 19 Sep 94 13:52:13 EDT
Received: from ncrgw1 by ncrhub1.NCR.COM id aa28734; 19 Sep 94 13:51 EDT
Received: by ncrgw1.NCR.COM; 19 Sep 94 12:19:35 EDT
    sendmail 8.6.9/UCSD-2.2-sun
    Mon, 19 Sep 1994 04:30:08 -0700 for tcp-digest-list
Received: by ucsd.edu; id EAA23619
    sendmail 8.6.9/UCSD-2.2-sun
    Mon, 19 Sep 1994 04:30:05 -0700 for tcp-group-ddist
Message-Id: <[e-mail]>
Date: Mon, 19 Sep 94 04:30:02 PDT
From: Advanced Amateur Radio Networking Group <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: TCP-Group Digest V94 #206
To: [e-mail]

TCP-Group Digest            Mon, 19 Sep 94       Volume 94 : Issue  206

Today's Topics:
                       Best asy speed settings?
                        remove old code W-NOS
                      Windows mailers for JNOS?

Send Replies or notes for publication to: <[e-mail]>.
Subscription requests to <[e-mail]>.
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: Sun, 18 Sep 1994 09:01:07 -0400 (EDT)
From: [e-mail]
Subject: Best asy speed settings?
To: [e-mail]

Given JNOS 1.10f running on a 386/20 with 16550s on all serial ports, what's
the best strategy for serial port speeds to the KISS TNCs?  We're looking at
a switch that will have two 9600 baud TNCs, and probably two 1200 baud ones,
as well as a couple of PI cards and an ethernet board.  It'll be a busy
machine...

To reduce latency, we would want to run the ports as fast as possible, at
least
2x the radio speed.  But from an interrupt and system loading perspective, are
there other considerations?  In particular, would we be better off running the
1200 baud TNCs with very fast serial speeds?  Or should we keep them at 2400
or 4800 baud?

I guess the real question is whether the system and UARTs  will be happier
with fast but infrequent bursts of data, or with longer but more constant
ones.

Any ideas?

John
--
John Ackermann   AG9V
Internet:  [e-mail]
Packet:    AG9V@N8ACV.#DAY.OH.USA

------------------------------

Date: Mon, 19 Sep 94 11:13:55 EST
From: BARRY TITMARSH <[e-mail]>
Subject: remove old code W-NOS
To: TCP-GROUP <[e-mail]>, wnos-group <[e-mail]>

Im going to remove old code from the basic W-NOS src tree
does any one that uses w-nos need to have:
defined HS
defined HAPN
defined EAGLE
defined PC100
defined APPELTALK

i want to remove these intercaes from the code completely
most users Dont need/use them.
speak now or its gone!
Barry Co-ord wnos.

------------------------------

Date: Sun, 18 Sep 94 20:37:42 EST
From: "Ted Rosen" <[e-mail]>
Subject: Windows mailers for JNOS?
To: [e-mail]3rpi

I recently received a response to my request for Windows based
smtp/nntp mailers which would work with JNOS (I'm using v110b),
pointing to gmail.exe. (gmail.zip at ucsd.edu)

The version of gmail.exe which I downloaded (206336bytes, 2/27/93)
had a couple of problems. The program would not delete mail files
when requested, and an options menu selection "preferences" was
not operational. Also there was no current help file, as indicated
in the enclosed readme file.

1. Has anyone had success running gmail? Is there a more current
version, or additional information which would assist in getting
the version which I have operational?

2. Are there other Windows based mailers which work successfully
with JNOS? If so what are the anonymous ftp sites?

3. I am posting this to both tcp-group and nos-bbs in hopes of a
more complete response.



Ted

Mailbox : VA3TAR @ VA3BBS.#SCON.ON.CAN.NOAM
AMPRNet : [e-mail] [44.135.88.129]
Internet: [e-mail]

------------------------------

End of TCP-Group Digest V94 #206
******************************

------------------------------

Date: Tue, 20 Sep 1994 23:12:02 -0800 (PDT)
From: [e-mail] (John Paul Morrison)
Subject: mtu oddity, jnos, and linux
To: [e-mail]

I tried running jnos instead of ka9q (DOS) as a router/gateway and I
noticed something really weird. I assume it's a jnos problem.


the network looks like:

(A) Linux 1.1.37 ====ether==== (B) JNOS 1.08c ----+
                                       56kbps packet
(D) Linux 1.1.47 ====== (C) Linux 1.1.47----+

In a nutshell, I had to change the mtu on (D) to 576, even though JNOS
was set to 1500, just as all the other machine mtu's are set to 1500
(both for ethernet and 56k packet, it's all mtu of 1500).

(A) can talk to (C) fine, but if (A) talks to (D), output from large
bursts of data ends up hanging the connection. ie I can do ls
OK in a small directory but it hangs in a directory with many files;
ftp works for tiny files but hangs on 1k files.

I *know* the mtu is set to 1500 on the jnos PI2 driver, unless jnos is
only pretending to set the mtu to 1500.  I also don't know why (A) to (C)
works, if it's indeed an mtu thing.


---------------------------------------------------------------------------
BogoMIPS Research Labs  --  bogosity research & simulation  --  VE7JPM  --
[e-mail] [e-mail] [e-mail]
---------------------------------------------------------------------------

------------------------------

Date: Tue, 20 Sep 94 14:08:55 BST
From: Martin Lines <[e-mail]>
Subject: SCC Testing
To: [e-mail], [e-mail]

Hi,

I have just built an SCC and was fooled by the testing method
described in the accompanying documentation.

The document describes how an SCC card without modems
can be tested by watching TXINTS increment when a
connect is issued on one of the scc ports.

I tried this and nothing happened. I then spent a while
checking the board etc but everything appeared ok.

Then when looking a SCC.C and SCC.H I realised that the
system works in CSMA mode by default. This meant that
as DCD was floating (ie no modem connected) the Transmit
would not take place.

Simply issuing the command

param <interface> 5 1

turns on full duplex operation and off went the TXINTS nicely.

Having got a working scc i can now turn to modems......



Regards

Martin Lines

Network Consultant
__________________________________________________________
Home:

||||| ||||| ||||||   [e-mail]. (no Internet)
|   | |       ||     G1SEO@GB7TXA
|   | |||     ||     22, Dowding Close
|   |    ||   ||     Woodley                [phone]
|   |     |   ||     Reading                [phone]
||||| ||||| ||||||   RG5 4NL . UK
__________________________________________________________
Work:
                     [e-mail]

                                            [phone]
                                       Fax: [phone]
__________________________________________________________

------------------------------

Date: Tue, 20 Sep 94 17:07:03 +0200
From: Henk Peek <[e-mail]>
Subject: SCC Testing
To: [e-mail], [e-mail], [e-mail]

Martin,

>I have just built an SCC and was fooled by the testing method
>described in the accompanying documentation.

>The document describes how an SCC card without modems
>can be tested by watching TXINTS increment when a
>connect is issued on one of the scc ports.
Normaly I test with conected modem. The modem is only
used for DCD level. Only this isn`t writen up in detail.

>I tried this and nothing happened. I then spent a while
>checking the board etc but everything appeared ok.
>
>Then when looking a SCC.C and SCC.H I realised that the
>system works in CSMA mode by default. This meant that
>as DCD was floating (ie no modem connected) the Transmit
>would not take place.
>
>Simply issuing the command
>
>param <interface> 5 1
>
>turns on full duplex operation and off went the TXINTS nicely.
>
>Having got a working scc i can now turn to modems......
>
Thanks, I add this to version 6 of the OptoPcScc documentation

Regards,

Henk Peek, PA0HZP

------------------------------

Date: Wed, 21 Sep 94 08:42:50 EST
From: BARRY TITMARSH <[e-mail]>
Subject: upload W-NOS.940921.zip [src]
To: TCP-GROUP <[e-mail]>, wnos-group <[e-mail]>

I will upload to ftp.ucsd.edu:...incoming
the latest src code for W-NOS version 940921
this has many bug fixes in the DAMA_slave code
an improved scc drsi interface for dama mode
thanks to dg1zx and dl6zba  who have worked on this
new dama implementation.  Some other minor bugs are fixed
and system stability improved, memory leak IS gone!
However this is only compiled with Borlandc C++ version 2.00
i cant confirm or test any other compiler and the performance of
W-NOS with other versions of C++.

Later today i will upload 2 .exe's one with just ASY and the other with SCC
all services included, in both. Also packet drivers.

file names:

wn940921.zip = source's
wn940921-asy.exe
wn940921-scc.exe


No Warrenty given std disclaimer stands.

 Barry gm8sau.dc0hk and the team. [see Credits:  in startup]

------------------------------

End of TCP-Group Digest V94 #208
******************************